-
-
Notifications
You must be signed in to change notification settings - Fork 670
Optimized for size Mathf.pow #1199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Speaking of paths, do you know if we are testing all possible combinations? Like currently we instantiate and run untouched and fully optimized, but nothing in between, which might make us miss something for certain ASC_XY levels. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still believe we should somehow test more variations of optimization options, just to make sure we are not missing a branch, since if something goes wrong on a user's end these things will be exceptionally hard to track down. Probably fine to not have fixtures for these, so just compile and run the tests on them. From the comments it seems that this PR is not affected specifically by that, so LGTM.
No description provided.